Method and system for asset routing

ABSTRACT

The method for asset routing can include: determining a digital asset, routing the digital asset to a print partner based on the mail parameters, optionally printing a physical version of each digital asset, and optionally drop-shipping the physical assets. However, the method can additionally or alternatively include any other suitable elements.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.63/323,837 filed 25 Mar. 2022 and U.S. Provisional Application No.63/336,131 filed 28 Apr. 2022, each of which is incorporated in itsentirety by this reference.

TECHNICAL FIELD

This invention relates generally to the mailing services field, and morespecifically to a new and useful method for asset routing.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart representation of a variant of the method.

FIG. 2 is a schematic representation of a variant of the system.

FIG. 3 is a flowchart representation of a variant of the method.

FIG. 4 is an illustrative example of a variant of the method.

FIG. 5 is an illustrative example of assigning digital assets toregional batches.

FIGS. 6-8 are illustrative examples of geo-routing.

FIG. 9 is an illustrative example of speed-based routing.

FIG. 10 is a flowchart representation of a variant of the methodincluding a decision tree-based algorithm.

FIG. 11 is an illustrative example of a mail partner and print partnerarchitecture that can be used with the system.

FIG. 12 is a flowchart representation of a variant of the method.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of the preferred embodiments of the inventionis not intended to limit the invention to these preferred embodiments,but rather to enable any person skilled in the art to make and use thisinvention.

1. Overview

As shown in FIG. 1 , the method for asset routing can include:determining a digital asset S100, routing the digital asset to a printpartner based on the mail parameters S200, optionally printing aphysical version of each digital asset S300, and optionallydrop-shipping the physical assets S400. However, the method canadditionally or alternatively include any other suitable elements. Themethod functions to route individual digital assets to different printpartners based on the delivery location of each digital asset whileminimizing or optimizing for time-to-delivery.

2. Examples

In an example, the method can include: batching digital assets fromdisparate orders into batches, each associated with a different carrierfacility (e.g., processing and distribution center (P&DC), Bulk MailCenter (BMC), etc.), based on the digital asset's permutation andrecipient destination inclusion within the geographic coverage of therespective carrier facility; selecting a print partner for therespective carrier facility and sending the batch to the print partnerfor physical asset printing (and optionally, carrier facility drop-off)when a batch satisfies a print condition at a cut-off time; and, whenthe regional batch does not satisfy the print condition by the cut-offtime, iteratively re-batching the digital assets into new batches basedon the geographic coverage of higher- and/or lower-level carrierfacilities until a print condition is met; selecting a print partner forthe carrier facility associated with a satisfactory batch; sending thebatch of digital assets to the selected print partner for physical assetprinting (and optionally, carrier facility drop-off); and optionallygeo-routing the digital asset if no satisfactory batch is found.

In an illustrative example, the method includes: determining a digitalasset (e.g., digital mail piece); assigning the digital asset to aregional batch based on the digital asset's permutation and recipientdestination; sending the regional batch to a (regional) print partnerfor physical asset printing when the regional batch satisfies the printcondition (e.g., includes at least a threshold amount of mail) by acut-off time (e.g., 5,000 digital assets, 100 lbs. of mail, etc.);rolling the regional batch up to a national batch when the regionalbatch does not satisfy the condition (e.g., include the threshold amountof mail) at the cut-off time, and sending the national batch to a(national) print partner when the national batch satisfies a secondcondition (e.g., includes a threshold amount of mail, the same ordifferent condition from that required for the regional batch, etc.),and geo-routing each digital asset of the national batch when thenational batch does not include the threshold amount of mail.Geo-routing a digital asset can include: routing the digital asset to alocal print partner associated with a carrier facility servicing thedigital asset's destination (e.g., the digital asset is within thecarrier facility's delivery zone or geographic region), wherein thedigital asset is preferentially routed to a local carrier facility,regional carrier facility, then national carrier facility, in thatorder. The digital assets within the batches can be from the same ordifferent order (e.g., received from the same or different entity).Digital assets from the same order can be individually routed or routedtogether. The digital assets can each be associated with a targetdelivery date (TDD), wherein a physical analog of the digital asset canbe routed, printed, drop-shipped, or otherwise managed on a datecalculated from the TDD.

3. Technical Advantages

Variants of the technology for asset routing can confer several benefitsover conventional systems.

First, enterprise marketers care about a digital asset reaching therecipient's mailbox within a certain date range (e.g., a target deliverydate+/−2 days). Conventionally, printers will print an entire order(e.g., all digital assets within a marketing campaign), and insert thedigital assets of the order into the mail stream at a single location(e.g., a local facility). However, because the mail partner system(e.g., carrier, such as USPS) is hierarchical, in the worst-casescenario, each digital asset can travel a long distance from the firstlocal facility, to a first regional facility, to a first nationalfacility, to a second national facility, to a second regional facility,and then to a second local facility before finally being delivered toeach digital asset's destination. In addition to adding transit time,the conventional method wastes energy (e.g., fuel) and manpower intransporting the physical assets over long geographic distances. Whileprint partners are capable of drop shipping batches of mail at regionaland/or national facilities to minimize the distance and/or deliverytime, this is not practically possible because the digital assets ineach order have geographically dispersed recipient destinations—aportion of the order's digital assets will need to go through the vastmajority of the local-regional-national-regional-local chain. Even ifportions of the order shared the same regional or national recipientregion, those portions cannot satisfy the minimum amount of mailrequired for drop shipping. Variants of the technology can overcome thischallenge and more reliably deliver a digital asset on time by splittingorders and aggregating the resultant individual digital assets byrecipient location until a threshold condition (e.g., minimum ordervolume) is satisfied to maximize the probability of drop-shipping (e.g.,postal drop shipping). Variants of the technology can further decreasefuel waste (e.g., improve physical asset distribution efficiency) and/ordecrease carbon expenditure facilitating physical asset generationproximal the distributing carrier facility and/or proximal the deliverylocation (e.g., by sending the digital asset to the print partnerassociated with the carrier facility and/or near the delivery locationfor printing). Variants of the technology can also accommodate the printpartners' inability to print a diverse set of asset permutations in asingle run by forming the digital asset batches by asset permutation(e.g., postcard, letter, letter size, whether an envelope is needed,etc.). In variants, the technology can guarantee delivery by a targetdate, even when using low-priority mailing channels (e.g., packageservices, marketing mail, periodicals, priority mail, etc.).

Second, variants of the technology can enable small-scale mailcampaigns, including those with as few as a single digital asset in anorder, to leverage the benefits of drop-shipping by aggregating digitalassets from multiple orders in order to satisfy the minimum amount ofmail required for drop shipping.

Third, variants of the technology can enable more flexible asset routingby continuing to aggregate digital assets into batches to aim fordrop-shipping up until a cutoff time soon before the production date, atwhich point the technology can determine an optimal fallback option fromamong multiple alternative routing schemes.

However, the technology can confer any other suitable benefits.

4. System

The method is preferably performed using a system including: a computingsystem, one or more routing systems, one or more routing controllers,one or more datastores, and/or any other suitable components (e.g.,example shown in FIG. 2 ). However, the method can additionally oralternatively be performed using any other suitable system. The systempreferably functions to route individual digital assets to differentprint partners based on the delivery location of each digital assetwhile ensuring that each digital asset is delivered within a specifictarget time range. However, the system can provide any other suitablefunction. The system is preferably fully automated, but can additionallyor alternatively request manual confirmation before executing any steps,accept manual inputs to override any automated processes ordecision-making, be dependent on triggers from an external system,and/or otherwise be controlled.

The system preferably processes one or more orders from one or moresenders. Each order preferably includes: one or more digital assets, anassociated order volume (e.g., number of digital assets), and one ormore timestamps (e.g., time at which the order was received, maximumtime allocation for time of order receipt to print, etc.), but canadditionally or alternatively include any other suitable information.

Each order can include one or more digital assets. Orders can bereceived as small asset orders (e.g., 1 or 2 pieces), mid-sized assetorders (e.g., 10, 30, 50, 60, 80 assets), bulk asset orders (e.g., withat least 100, 200, 500, or more assets), but can alternatively be or beotherwise sized.

The digital asset can be unique (e.g., each digital asset can havedifferent asset parameters, images, and/or otherwise differ from otherassets within the order), but can alternatively be generic or non-unique(e.g., have the same asset parameters, have the same graphics, etc.), orbe otherwise related. The assets within an order are preferablyaddressed to different recipients, but can alternatively be addressed tothe same recipient.

The digital asset of an order is preferably a press ready proof (e.g.,ready for print), but can additionally or alternatively be proofparameters, the raw constituent components of a proof, or have any othersuitable format. The proof can be represented: as a PDF, in HTML, as animage (e.g., PNG, JPG, etc.), and/or any other suitable digital format.

Each digital asset can be associated with an asset identifier. The assetidentifier can be: globally unique, unique within a batch, temporallyunique, nonunique, or otherwise determined. The asset identifier can beassociated with: a mail sender, a mail recipient, an order identifier,and/or any other suitable information.

In a first variation, the order is represented as a JSON object thatadheres to an API, but can additionally or alternatively be an XML,YAML, plain text, and/or any other suitable data structure. The ordercan be received as a programmatic function associated with an array. Thearray can specify different parameter values for each recipient, whereinthe system can automatically generate each asset for a given recipientbased on the programmatic function and respective values from the array.

The digital asset is preferably associated with a set of mailparameters, which can include: asset parameters (e.g., defining thepermutation), delivery information, and/or other information.

The mail parameters can include asset parameters (e.g., metadata,specifications, etc.), which can include: type (e.g., letter, postcard,pamphlet, etc.), color (e.g., black and white, color, etc.),perforation, priority (e.g., first class, standard, fragile, etc.), size(e.g., dimensions such as length width, number of sheets, etc.), paperpoundage, coating, form factor, imagery, quality (e.g., imageresolution, pixel resolution, pixel density, dpi, etc.), deliveryinformation, and/or any other suitable parameter. Mail parameters can beassociated with the digital version of the digital asset and/or anintended physical version (e.g., a physical analog) of the digital assetafter printing.

The mail parameters can include delivery information, which can include:a delivery location (e.g., recipient location; an address, geolocation,a zip code, a 3-digit zip code, a 5-digit zip code, etc.), a deliverytimeframe (e.g., target delivery date and/or date range, mail by date,etc.), a recipient, and/or any other suitable information.

The mail parameters can include a permutation, which can function todefine a combination of the asset parameter values associated with adigital asset. The permutation is preferably defined by a subset of theasset parameter values associated with a digital asset (e.g., all butthe address and recipient), but can alternatively be defined by all theasset parameter values associated with a digital asset. The permutationcan be associated with a fixed combination of values (e.g., wherein eachvalue must meet a specific requirement). The permutation canalternatively be associated with a flexible combination of assetparameter values (e.g., wherein one or more values can vary according toa preference range, a set of fallback options, and/or other parameters).In an example, a value must meet a baseline condition buy may exceed thecondition (e.g., wherein the image resolution must be at least acustomer-specified resolution).

However, an order can additionally or alternatively be otherwisedefined.

The system can assign a digital asset to a batch. A batch is preferablya group of assets, different from an order, that can be transferred froma print partner to a delivery service. A batch can include digitalassets from a plurality of orders, digital assets from a single order,and/or include any other suitable digital assets. Each batch ispreferably associated with a single carrier facility (e.g., P&DC), butcan alternatively be associated with multiple carrier facilities (e.g.,a low-level P&DC and higher-level P&DCs that encompass the low-levelP&DC), with a geographic region, with a print partner, and/or with anyother suitable entity. Each batch is preferably sent to a single printpartner for printing, but can alternatively be sent to multiple printpartners for printing, or not associated with a print partner. Eachprint partner can host one or more batches (e.g., concurrently orserially).

A batch can be associated with a threshold condition (e.g., minimumorder volume/quantity, etc.), which can determine whether the batchshould be sent to the print partner for printing, and/or whether thedrop-ship requirements have been met. The threshold condition can bepredetermined, determined by a delivery service (e.g., minimum volume todrop-ship, minimum quantity to drop-ship, etc.), determined by the printpartner (e.g., minimum volume to print a batch), determined using anoptimization (e.g., an optimization over cost, expended fuel, etc.),and/or otherwise determined). The minimum volume and/or quantity can beof: individual assets, individual digital asset proofs (e.g., a uniqueasset design), and/or any other suitable asset unit.

A batch can be associated with a timeframe (e.g., single business day,span multiple days, etc.). The timeframe can be: a printing timeframe(e.g., the physical assets must be printed within a predeterminedtimeframe), a mailing timeframe (e.g., the physical assets within thebatch must be handed off to the delivery service within a predeterminedtimeframe), a delivery timeframe (e.g., the physical assets must bedelivered to a recipient within a predetermined timeframe), and/or anyother suitable timeframe.

A batch can be associated with one or more requirements. Batchrequirements can include a permutation, which can define an acceptablecombination of asset parameter values for a given batch (e.g.,acceptable asset parameter values that can be printed together on theprint partner machinery). The permutation preferably specifies valuesfor a subset of the asset parameters, such that a batch can acceptdigital assets with different asset parameter values, but canadditionally or alternatively specify values for the full set of assetparameters. In an example, the permutation specifies the size and imagequality of the digital assets to be printed, but leaves the weight assetparameter flexible. Batch requirements can be stored in the datastore,and/or otherwise stored. Batch requirements can be specified by eachprint partner's machinery capabilities, machine setup, manually (e.g.,specified by a print partner, by a system administrator, etc.),automatically determined (e.g., specified by a printing machine;determined based on: the type of machines associated with the printpartner, the machines' possible configurations, the batch parametersassociated with each configuration, the print partner machine setuprequired to print the digital assets in an existing batch, etc.), and/orotherwise determined. Batch requirements can be received through agraphical user interface (GUI), a print partner machine interface, orany other suitable interface. The GUI is preferably configured tocollect batch requirements for the routing system (e.g., informationregarding print partners, regarding modules of the routing system,etc.). The batch requirements can be received: over a wired or wirelessconnection (e.g., the Internet), a CAN or field bus, and/or any othersuitable connection.

However, a batch can be otherwise defined.

The system and method can be used with one or more third-party services.Third party services can include: mail partners, print partners, and/orany other suitable party.

The third-party services can include a set of carriers (e.g., mailpartners, delivery services, etc.) that function to receive physicalassets (e.g., from one or more print partners, from the platform, etc.)and deliver the physical assets to recipient locations using one or morecarrier architectures. Examples of mail partners can be: USPS, RoyalMail, FedEx, UPS, and/or any other suitable carrier. The systempreferably interfaces with a plurality of mail partners, but canadditionally or alternatively interface with a single mail partner. Themail partner is preferably associated with a set of mail partnerparameters, such as minimum batch volume, maximum batch volume, mailbatch parameters, pickup times, cost, speed, associated print partners,and/or any other suitable parameter. The mail partner parameters can be:globally applicable, applicable to a route, a geographic region, atimeframe, and/or otherwise limited.

The mail partner's carrier architecture can include: one or more carrierfacilities (e.g., processing and distribution centers (P&DCs), Bulk MailCenter (BMC)) that process and/or distribute physical assets (e.g.,physical mail assets). For example, a mail carrier can include aplurality of carrier facilities, including: one or more localfacilities, one or more regional facilities, one or more super-regionalfacilities, one or more national facilities, and/or any other suitablefacilities (e.g., example shown in FIG. 11 ). Each facility ispreferably capable of receiving drop-shipped batches of assets (e.g.,wherein an entity, such as a print partner, can drop off a batch ofphysical assets at the carrier facility for processing and furthermailing), but can alternatively lack the capability. Each facility ispreferably associated with a different geographic region (e.g., coverageregion, delivery region, delivery zone, etc.) specific to the facility.The facilities are preferably hierarchical, such that each higher-levelfacility is associated with (e.g., shares a geographic region with,receives and/or delivers to, encompasses the geographic region of, etc.)one or more associated lower-level facilities. The lower-levelfacilities can be associated with higher-level facilities when thelower-level facilities are located within the higher-level facility'sgeographic region, when the geographic regions of the lower- andhigher-level facilities overlap, when the lower-level facility sendsphysical assets to or receives physical assets from the higher-levelfacility, be associated by the mail partner, or be otherwise associatedwith a higher-level facility. Lowest-level facilities (e.g., localfacilities) can pick up and/or deliver physical assets from and/or torecipient locations within their geographic regions. In operation,lower-level facilities that receive physical assets (e.g., mail) outsideof their geographic region sends the physical asset to successivelyhigher higher-level facilities until the higher-level facility'sgeographic region encompasses the delivery location, at which point thehigher level facility sends the physical asset down to successivelylower-level facilities until the physical asset is sent to alowest-level facility (e.g., local facility) encompassing the deliverylocation. The physical asset is then sent from the lowest-level facilityto the delivery location. However, the facilities can otherwise interactwith each other.

In an example, a local facility is a destination delivery unit (DDU)such as a local post office that is associated with a limited geographicregion (e.g., associated with a single zip code, associated with severalzip codes, etc.). In a second example, a regional facility is asectional center facility (SCF) that is associated with a geographicregion larger than a local facility, wherein the geographic regionencompasses one or more geographic regions of local facilities. In athird example, a super-regional facility (e.g., national facility) is anetwork distribution center (NDC) that is associated with a geographicregion larger than a regional facility, wherein the geographic regionencompasses one or more geographic regions of regional facilities.

The third-party services can include a set of print partners thatfunction to generate or create physical versions of a digital asset(e.g., print the digital asset). The print partners can: print physicalversions of the digital assets, determine a mail stream insertion datefor a digital asset based on the respective target delivery date, holddigital assets until the carrier insertion date, insert the digitalasset into the mail stream (e.g., individually or as a batch; dropshipped to a carrier facility or otherwise shipped; etc.), and/orperform other functionalities. The system preferably interfaces with aplurality of print partners, but can additionally or alternativelyinterface with a single print partner.

Each print partner can be associated with a set of print capabilities,but can alternatively not be associated with print capabilities. A printcapability can specify whether the print partner is capable of printingan asset with a certain variable value (e.g., attribute value, etc.).Mail variables can include: mail type (e.g., postcards, self-mailers,letters, checks, etc.), perforation, color, size, shape, and/or anyother physical and/or visual mail attribute. A combination of mailvariable values (e.g., color self-mailer with a 3″×3″ envelope) can bereferred to as a mail permutation, wherein different print partners canbe capable of printing different mail permutations, based on theirprinting capabilities. For example, a print partner associated withcertain capabilities can print certain mail variable permutations butcannot print other mail variable permutations. Each print partner canhave one or more machines, wherein each machine can have one or moreconfigurations, wherein each configuration can have differentcapabilities, but can be otherwise configured. Different print partnerscan have different machines with different configurability, andtherefore be associated with different capabilities. The set ofcapabilities can be determined based on the print partner's machinery,be manually specified by the print partner, be determined based on theasset parameters of prior assets printed by the print partner, or beotherwise determined.

Each print partner can be associated with a capacity. The capacity ispreferably an overall digital asset volume for a given timeframe, butcan alternatively be a digital asset rate or be any other capacity. Thecapacity is preferably a maximum limit, but can alternatively be aminimum or any other limit. The capacity can be associated with: theprint capability (e.g., the mail permutation), the printer themselves,and/or otherwise determined. Capacities can vary per print printer:annually, quarterly, monthly, daily, hourly, by the minute, and/or anyother suitable time interval.

Each print partner can be associated with one or more geographiclocations (e.g., the geographic location of the print partner's printfacility).

Each print partner can be associated with one or more carrierfacilities. Each print partner can be associated with one or more localfacilities, one or more regional facilities, one or more super-regionalfacilities, and or any other suitable number of facilities. Each printpartner can be associated with a facility (e.g., local facility,regional facility, super-regional facility, etc.) when the print partnerlocation is located within the respective region (e.g., associated withthe facility), be associated with the carrier facility that it isgeographically closest to, be associated based on travel distance ortravel time to the carrier facility, be otherwise associated with acarrier facility, and/or not be associated with a facility. Each printpartner can drop batches of physical assets off at the one or moreassociated carrier facilities, facilitate physical asset batch drop-offat the carrier facility (e.g., using an intermediary carrier ortransport entity), facilitate physical asset pickup by the carrier,and/or otherwise transfer the physical asset to the carrier facility.

However, the third-party services can additionally or alternativelyinclude any other suitable elements.

The system preferably includes a computing system, which functions toperform one or more elements of the method. The computing system can bea remote computing system (e.g., server system), a distributed computingsystem, and/or other computing system. The computing system can executethe routing system and/or portions thereof.

The system preferably includes one or more routing systems. The routingsystem preferably functions to determine a carrier facility and/or aprint partner for a set of digital assets, but can additionally oralternatively determine a prioritized list (e.g., with weightedpriority) of print partners or carrier facilities, determine a printpartner or carrier facility for an order, and/or provide any othersuitable functionality. The routing system is preferably accessible viaone or more APIs, but can be otherwise accessible.

The routing system preferably includes one or more modules. The modulescan include any number of the following modules, arranged in any othersuitable order. The modules can include a: capability module, batchmodule, preference module, capacity module, carrier routing module,geo-routing module, printer communications module, carriercommunications module, and/or any other suitable module.

The capability module, the batch module, the preference module, and thecapacity module can be the modules described in U.S. patent applicationSer. No. 17/540,521, filed 2 Dec. 2021, which is incorporated herein inits entirety by this reference.

The modules can include a carrier routing module, which can function todetermine a target carrier facility for the batch, determine a printpartner for the batch, and/or otherwise function.

The carrier routing module can determine a target carrier facility basedon: a delivery destination region for the batch, proximity of a printpartner, a preference associated with a nearby print partner, a costassociated with a nearby print partner, a cost associated with deliveryfrom the target carrier facility to the delivery addresses of the batch,and/or any other factors. The carrier routing module can use rule sets,heuristics, optimization, models, and/or any other method to route thebatch. In examples, the carrier routing module can perform any of themethod steps described in S150 or S200, and/or perform any othersuitable step.

However, the carrier routing module can be otherwise configured.

The modules can include a geo-routing module, which can function torouting a digital asset to a capable print partner within a region basedon the delivery destination.

The geo-routing module can route a digital asset: to a capable printpartner that is closest to the delivery location, to the print partnerwith the highest-preference within a delivery region of the digitalasset (e.g., within the same zip code as the digital asset, within 20miles of the digital asset, etc.), to the lowest-level facilityservicing the digital asset's delivery location, to the lowest-levelcarrier facility servicing the digital asset's delivery location with acapable print partner within a specified range of the carrier facility(e.g., within the service zone of the carrier facility), and/orotherwise route the digital asset. The geo-routing module can use rulesets, heuristics, optimization, models, and/or any other method to routethe digital asset. In examples, the geo-routing module can perform S200,and/or perform any other suitable step.

However, the geo-routing module can be otherwise configured.

The modules can include a printer communications module which canfunction to enable the system to communicate with print partners. Theprinter communications module can access information (e.g., from awebsite, via a survey, manually by phone call, etc.) about a printpartner's capabilities, capacity, coverage zone, location, upcomingdelays, and/or other information that can be used as inputs for themethod. Print partner information can be retrieved by querying thedatastore, querying a print partner API, and/or be otherwise retrieved.The printer communications module can send information to the printpartner regarding orders, order updates, and/or other suitableinformation.

However, the printer communications module can be otherwise configured.

The modules can include a carrier communications module, which canfunction to enable the system to communicate with mail carriers. Thecarrier communications module can access information (e.g., from awebsite) relevant to mail carrier requirements (e.g., minimum drop-shipvolume, etc.), service interruptions, coverage regions, and/or otherinformation that can be used as inputs for the method.

However, the carrier communications module can be otherwise configured.

The system preferably includes a routing controller that functions tocoordinate routing system activities and/or interface the routing systemcomponents. The routing controller preferably interfaces with a printpartner (e.g., via a print partner API) and the routing system, but canadditionally or alternatively interface with a graphical user interface(e.g., presented to the sender), and/or interface with any othersuitable party. The routing controller preferably accesses/queries thedatastore. The routing controller can update the ruleset in thedatastore. The routing controller can transmit rulesets to one or moremodules of the routing system (e.g., periodically, such as for everydigital asset, every 10 assets, every digital asset, every 5 minutes,every hour, etc.; after a rule and/or ruleset update; and/or at anyother suitable time). The routing controller can additionally oralternatively communicate volume parameters and/or thresholds to one ormore modules of the routing system. The routing controller can receivefailed digital assets from the fail queue, orphaned digital assets fromthe orphan queue, and/or receive any other suitable digital assets. Therouting controller can transmit received digital assets to the mailqueue, directly to the routing system, to a different system capable ofdetermining a batch associated with a print partner for the specifieddigital asset, and/or otherwise transmit the digital asset.

However, the routing controller can be otherwise configured.

The system preferably includes one or more datastores. The datastore canpreferably be queried, but can be otherwise configured. The datastorescan include one or more: module datastores, capacity datastores, queues,print partner databases, carrier databases, and/or any other suitabledatastore. The data stored in the datastores can be determinedautomatically (e.g., via print partner APIs, manufacturing machine APIs,the routing controller API, the GUI, etc.), manually (e.g., by a serviceadministrator), and/or otherwise determined.

The print partner database can store information per print partner(e.g., machine capabilities, counters, etc.) and/or any other suitableinformation. The information per print partner can include: currentlyavailable capacity per print partner, such as one or more counters(e.g., for one or more time periods, batch counters per print periodsuch as the number of digital assets in a batch in a given productionperiod; monthly volume counters such as the number of digital assetsand/or orders sent to the print partner in a given month, etc.);capability per print partner (e.g., print permutations that each printpartner can print, based on all print partner machinery, the batchparameters, etc.); facilities (e.g., mail carrier facilities) the printpartner can delivery to; processing times (e.g., time to upload aquantity of digital assets to the print partner processing system, timeto print an order of a specified volume, time to postal drop ship, timeto deliver to a mail carrier facility, etc.); prices (e.g.,);requirements (e.g., minimum order volume, acceptable asset parameters,required advance notice time for an order, etc.); one or more weightparameters (e.g., weight priority based on a volume target, volumethreshold, batch volume target, and/or batch volume threshold, etc.);and/or any other suitable information. The information per print partnercan additionally be stored: per batch, per time period, per order type(e.g., standard order versus drop shipping order); and/or otherwisespecified. The weight parameter can be determined automatically (e.g.,by the routing controller API) and/or manually (e.g., by a serviceprovider). The weight parameter can be based on capacity, existing/openbatch size(s), monthly quota associated with the routing system, dailyquota associated with the routing system, and/or otherwise based.Information stored in the print partner database can be: received fromthe print partner, collected about the print partner (e.g., historicaldata), predicted, and/or otherwise determined.

However, the print partner database can be otherwise configured.

The carrier database can store information per mail carrier, per mailcarrier facility, and/or any other suitable information. Informationstored in the carrier database can be: published (e.g., on a website,press brief, brochure, etc.) by, received (e.g., in an email, as adirect quote, on a call, etc.) from, tracked in association with, orotherwise determined about one or more mail carriers and/or mail carrierfacilities. Information stored in the carrier database can include:prices, services, quotas, requirements, restrictions, shipping timeestimates, actual historical shipping times, other historical data,regions serviced per carrier facility, regions serviced per carrier,holiday schedules, closures, and/or any other information.

However, the carrier database can be otherwise configured.

The datastores preferably include one or more queues, but canadditionally or alternatively include sorted lists, hashed set, and/orany other suitable collection of digital assets. Digital assets storedin the queue(s) can be retrieved or enqueued by the routing controllerAPI, by the routing system, and/or by any other suitable entity. Thequeues can include one or more: mail queues, orphan queues, fail queues,or any other suitable queue.

The datastore preferably includes one or more mail queues. The mailqueue can store all digital assets and/or orders received in S100 (e.g.,wherein the queue holds each digital asset prior to assigning thedigital asset to a batch). Another optional mail queue (e.g., the orphanqueue) can store digital assets and/or orders with no associated batch(e.g., no associated print partner) and/or any other suitable digitalasset. Another optional mail queue (e.g., the fail queue) can storedigital assets that the routing system could not process (e.g., batchrequirements were not satisfied, module requirements were not satisfied,etc.). Another optional mail queue (e.g., the geo-routing queue) canstore digital assets assigned to be geo-routed. Another optional mailqueue (e.g., the carrier facility queue) can store digital assets (e.g.,a batch) assigned to a carrier facility and/or print partner.Optionally, digital assets can be sent one at a time from a queue to theprint partner.

However, the datastore can be otherwise configured.

In variants, the method can be used with the system or componentsthereof described in U.S. application Ser. No. 17/127,125 filed 18 Dec.2020, which is incorporated herein in its entirety by this reference.

However, the system can include any additional and/or alternativecomponents.

5. Method

The method can include: determining a digital asset S100, determining abatch for the digital asset based on the delivery destination S150,routing the digital asset to a print partner based on the mailparameters S200, optionally printing a physical version of each digitalasset S300, and optionally drop-shipping the physical assets S400,and/or any other suitable elements. One or more instances of the methodcan be repeated for different digital assets, timeframes (e.g., daily,weekly, etc.), and/or otherwise repeated. All or portions of the methodcan be performed continuously, recurrently (e.g., daily, hourly, etc.),upon receipt of a request, and/or at any other time and/or frequency.

The method can leverage direct physical delivery of physical assets to afacility (e.g., “drop-shipping”), thereby bypassing intermediary stops.The physical assets are preferably drop-shipped to a regional facilityand/or a super-regional facility, but can additionally and/oralternatively be drop-shipped to a local facility, a mailbox, and/or anyother suitable location. Drop-shipping is preferably associated with athreshold condition such as a saturation condition, but canalternatively not be associated with a threshold condition. Thesaturation condition is preferably associated with a minimum ordervolume (e.g., number of mail pieces and/or physical volume, a quantityof digital assets assigned to a batch exceeding a threshold value,etc.), but can alternatively be associated with a minimum weight (e.g.,digital asset weight), a maximum weight, a maximum volume, and/or anyother suitable threshold. Examples of a saturation condition can be: 100digital assets, 1000 digital assets, 3000 digital assets, 5000 digitalassets, 100 pounds of mail, 12 linear feet, one layer of letter trays,number of standard pallets, and/or any other suitable range therein. Thesaturation condition can be the same or different for each facility,each print partner, each mail partner, each geographic region, and/ordifferent for each facility, each print partner, each mail partner, eachgeographic region. The saturation condition can be: predetermined,dynamically determined, manually determined, automatically determined,and/or otherwise determined. The saturation condition can be determinedby a mail partner (e.g., by the carrier, by the carrier facility, etc.),determined by a print partner, by a sender, determined using anoptimization across cost of time and transport (e.g., monetary cost,environmental impact, etc.), and/or otherwise determined. For example,the saturation condition is dynamically determined by calculating aminimum volume based on an estimated transportation cost (e.g., freightcost, freight cost less carbon credits, etc.).

The method can be performed daily, before a production cutoff time(e.g., deadline to guarantee a physical asset printing within apredetermined time period, such as same-day printing), before a routingcutoff time (e.g., predetermined time before production cutoff time suchthat there is enough time to print a batch satisfying the saturationcondition), upon receipt of a new order, upon receipt of a thresholdnumber of new orders, and/or at any other suitable time and/orfrequency.

5.1. Determining a Digital Asset S100.

S100 preferably functions to receive and process a digital asset forrouting. The digital asset can be one digital asset, multiple digitalassets, and/or any other suitable number of digital assets. The digitalassets can be concurrently received from one or more users (e.g.,senders, customers, service providers, etc.), but can alternatively beserially received from one or more users. The digital asset can bereceived as part of an order including multiple digital assets withdifferent delivery addresses, or received individually. The digitalasset can be: specified in HTML, be a print ready PDF (e.g., generatedfrom an HTML specification), be an InDesign document, and/or be in anyother suitable format. The digital asset is preferably a digital asset,but can alternatively be a document, a model (e.g., of a 2D object, of a3D object, etc.), and/or any other suitable digital asset.

The digital asset is preferably associated with mail parameters, but canalternatively not be associated with mail parameters. Mail parametersinclude: a target delivery date and/or date range, a delivery location(e.g., an address, a 3-digit zip code, a 5-digit zip code, etc.), afacility, a permutation (e.g., combination of mail variable values),and/or any other suitable mail parameters.

The delivery location (e.g., recipient location) can be associated withone or more local facilities, one or more regional facilities, one ormore super-regional facilities, and/or any other suitable facilities.The delivery location can be associated with a facility when thedelivery location is located within the respective region (e.g.,associated with the facility), but can alternatively be otherwiseassociated with a facility, and/or not be associated with a facility.

The digital asset can be associated with a permutation. The permutationcan be a combination of values for: a form factor, a size, a paperpoundage, a coating, and/or any other suitable mail variable. Examplesof variables include: a type (e.g., postcard, letter, etc.), a color(e.g., black and white, color, etc.), perforation, priority (e.g., firstclass, standard, etc.), size (e.g., dimensions such as length, width,number of sheets, etc.), imagery, mail by date, delivery date, deliverylocation (e.g., delivery address, zip code, etc.), quality (e.g., imageresolution), and/or any other suitable parameter.

The digital asset is preferably received as part of an order (e.g., amail order), but can alternatively be received individually or otherwisereceived. One or more orders from one or more senders can be received bythe system within a given routing period (e.g., time period betweencutoffs). Each order preferably includes multiple digital assetscontemporaneously received from the same entity, but can alternativelybe a single digital asset, multiple digital assets contemporaneouslyreceived from different entities, and/or otherwise defined. Digitalassets in the order can have the same permutation or differentpermutations. Digital assets in the order preferably have differentrecipients, but can alternatively have the same recipient. Digitalassets in the order preferably have different delivery locations, butcan alternatively have the same delivery location. Digital assets in theorder can have the same target delivery date or different targetdelivery dates. For example, an order from a single entity can include aplurality of digital assets, all to be delivered by the same targetdelivery date, wherein each digital asset of the plurality can includethe same logo (e.g., the entity's logo), different visual assets (e.g.,background images, foreground images, etc.), and different recipientinformation (e.g., different delivery locations). The plurality ofdigital assets can also include a variety of different form factors(e.g., some digital assets are postcards, while others are mailers).

Determining a digital asset can optionally include splitting an orderinto individual digital assets, wherein each individual digital assetcan be treated (e.g., routed) independently. Alternatively, multipledigital assets from a given order can be treated (e.g., routed) togetheras a unit. The digital assets from different orders can be reorganizedinto different batches, wherein the digital assets within each batch canshare a common: permutation, delivery region, target delivery timeframe,carrier facility, print partner, and/or other mail and/or assetparameter values (e.g., in S150). Alternatively, the orders can be splitand/or recombined randomly, manually, and/or otherwise split.

However, the digital asset can be otherwise determined.

5.2. Determining a Batch for the Digital Asset S150 Based on the MailParameters.

The method can optionally include determining a batch for the digitalasset based on the mail parameters S150, which functions to determine aset of other digital assets with which to print and mail the digitalasset. Each batch (e.g., digital asset set) can include digital assetsfrom the same or different order. The digital assets within each batchcan share one or more mail parameter values (e.g., location,permutation, target delivery date, etc.), and/or be unrelated. Eachbatch can include: a single digital asset, a plurality of digital assets(e.g., from one or more mail campaigns, one or more orders, etc.),and/or any other number of digital assets; example shown in FIG. 5 .

A set of digital assets can subsequently be routed to a printer (e.g.,in S200) and delivered in a batch to reduce production costs and enabledrop-shipping the entire batch. S150 can be performed continuously(e.g., immediately after S100, upon receipt of each new order, after astart time, etc.), after a requirement is met (e.g., once every digitalasset in an order of a specific size is received), recurrently (e.g.,daily, hourly, etc.), upon receipt of a request, and/or at any othertime and/or frequency. In a first example, the digital assets areimmediately assigned to batches upon order receipt, wherein batches forfuture print dates can be held until said print date. In a secondexample, the digital assets can be held until the associated print date(e.g., determined based on the respective delivery date and estimatedprint and delivery time), then assigned to a batch on the print date.However, the digital assets can be batched at any other time. S150 canbe performed prior to S200, as a step of S200, and/or otherwiseperformed. S150 can include determining an initial batch (e.g., aregional batch) for a digital asset, determining a new batch for adigital asset (e.g., example shown in FIG. 12 ), and/or other processes.

Preferably, a batch is determined for the digital asset such that thedigital assets of the batch all share a common delivery region (e.g.,common delivery destination region, the same zip code, all deliverydestinations within a specified range of a common carrier facility, alldelivery destinations within a range of a common print partner, commonmail carrier facility coverage zone, etc.) and a common deliverytimeframe (e.g., wherein all digital assets in a batch share a targetdelivery date, wherein all digital assets in a batch have an overlappingtarget delivery date range, etc.), however the batch can be otherwisedetermined. In an example, all delivery destinations fall within thecoverage zone of a common carrier facility. Optionally, the digitalassets of the batch all share a common permutation. The digital assetsof the batch can additionally or alternatively share any other mailparameter values, or not share one or more mail parameter values. Invariants, a digital asset that is received with fixed asset parametervalues can be assigned to a batch sharing that exact permutation. Inalternative variants, a digital asset that is received with flexibleasset parameter values can be assigned to a batch with a permutationthat meets the baseline asset parameter values for the digital asset.

Batches can be formed on the basis of one or more shared: geographicregion (e.g., the digital assets in the batch are associated withdelivery locations in the same delivery region, or are assigned to beprinted in the same print location, etc.), carrier facility (e.g., thedigital assets in the batch are assigned to the same carrier facility),print partner (e.g., wherein the digital assets in a batch have all beenassigned to the same print partner), delivery timeframe (e.g., whereinthe digital assets in a batch are intended to be delivered in the sametimeframe), permutation (e.g., the digital assets in a batch have thesame permutation values), and/or on another basis. The batches can beformed as the digital assets are being sorted (e.g., the digital assetsare sorted into a batch), after the digital assets have been sorted(e.g., the digital assets are assigned to a carrier facility, thenbatched together), and/or formed at any other time.

In a first variant, determining a batch for the digital asset caninclude creating a new batch. A new batch can be created if no existingbatch exists that shares the same delivery destination region,permutation, and delivery timeframe with the digital asset; if anappropriate batch exists but the quantity of assets already assigned tothe batch exceeds a limit (e.g., a standard order volume, based on thecapacity of a print partner, etc.); upon receipt of a command; and/orfor any other reason.

In a second variant, determining a batch for the digital asset caninclude assigning the digital asset to an existing batch before thebatch is routed to the print partner (e.g., before S200).

In a third variant, the digital asset can be assigned to an existingbatch that has already been routed to a print partner (e.g., afterS200). In this variant, further digital assets can continue to beassigned to the batch up until a cutoff condition is reached (e.g., acutoff time, a maximum batch size, etc.).

In a fourth variant, determining a batch for the digital asset can berepeated multiple times with varying constraints. For example, batchesof digital assets can be formed at different levels of the carrierfacility hierarchy until a print condition is met (e.g., the batchsatisfies a minimum drop-ship volume). Batch formation at differentcarrier facility hierarchical levels can be performed: at a cutoff time,iteratively according to a rule, randomly, concurrently (e.g., whereinthe digital asset is assigned to multiple batches for different carrierfacilities at the same time), and/or otherwise performed. In a firstexample of an iterative batching rule, batches are formed starting atthe lowest carrier facility level that can accept a drop shipment, thenformed at sequentially higher rising carrier facility levels when aprint condition is not met (e.g., wherein each subsequent carrierfacility services a larger region fully or partially encompassing theprior carrier facility coverage zone). In a second example of aniterative batching rule, batches are formed in reverse carrier facilitytransfer order, such that batches are preferentially formed at the lastcarrier facility before physical asset delivery to the deliverylocation, then formed at the carrier facility that transfers thephysical asset to the last carrier facility, proceeding backward throughthe order in which the physical asset is transferred to the deliverylocation. In a third example of an iterative batching rule, batches areformed at the regional carrier facility level first, then at thenational carrier facility level, then at a secondary regional carrierfacility underneath the national carrier facility (e.g., wherein thefirst and second regional carrier facility share a common nationalcarrier facility), then using alternative batching methodologies (e.g.,routing to the print partner closest to the delivery location,geo-routing the digital asset, etc.). At each stage, the method canoptionally include attempting to roll lower-level carrier facilitybatches (e.g., saturated or unsaturated) into higher-level carrierfacility batches to saturate the higher-level carrier facility batches,roll up smaller regional batches into national batches and/or adjacentregional batches to saturate said batches, combine batches withdifferent asset permutations that are also assigned to the same carrierfacility (e.g., wherein the batches can satisfy a print partnerrequirement for a printing run, do not individually satisfy a drop-shipminimum volume, but do satisfy the drop-ship minimum volume incombination), and/or otherwise combine or sub-combine the batches.However, batches can be formed (e.g., treating the carrier facilityhierarchy as a tree) using: depth-first search (e.g., pre-order,in-order, post-order, reverse pre-order, reverse post-order, reversein-order, etc.), breadth first search, level-order traversal, reverselevel-order traversal, bottom-up traversal, Monte-Carlo tree search,and/or any other suitable rule can be used. In an illustrative example,a digital asset can be assigned to an initial batch based on therespective delivery location, wherein the batch is associated withcarrier facility service zone of a common regional facility thatencompasses the delivery location. At a cutoff time, if the initialbatch is too small, each digital asset of the batch can be re-assignedto a new batch. Optionally, the digital asset can be re-assigned to anew batch, wherein each digital asset of the new batch falls within thecarrier facility service zone of a common super-regional facility (e.g.,where all of the other assets of the original batch join the new batch).Alternatively, the digital asset can be re-assigned to a new batch,wherein each digital asset of the new batch falls within the carrierfacility service zone of a local facility (e.g., where only a subset ofthe other assets of the original batch joins the new batch). In thisexample, the batches can also be formed on the basis of the digitalassets' permutation (e.g., each batch includes a single permutation;different batches are formed for each carrier facility for each assetpermutation). Alternatively, the batches can include a plurality ofasset permutations, wherein a print partner capable of printing the setof asset permutations in the batch can be selected to print said batch.In examples, the print partner can be selected and/or the batch can besent to the print partner when each permutation-specific sub-batch ofdigital assets satisfies the print partner's requirements to print thepermutation (e.g., each permutation-specific sub-batch satisfies aminimum print volume). However, digital asset batch assignment and/orre-assignment can be otherwise iteratively performed.

In a fifth variant, a batch can be determined for a digital asset withflexible asset parameter values. Optionally, a default asset parametervalues can be assigned to the digital asset, and any of the priorvariants can be used to determine the batch. Additionally oralternatively, a batch is determined with a permutation that satisfiesthe baseline conditions for the digital asset. In a first specificexample, a digital asset can be received with a requirement for aspecific pixel resolution, but can be assigned to an existing batch witha higher pixel resolution. In a second specific example, determining abatch for a digital asset with a flexible permutation can include:assigning the digital asset the minimum baseline asset parameter value(e.g., 200 dpi) by default, assigning the digital asset to alower-quality batch (e.g., a batch with a 200 dpi image qualityparameter) in accordance with the minimum baseline asset parametervalue, and optionally merging the lower-quality batch with ahigher-quality batch (e.g., a batch with a 300 dpi image qualityparameter) when a cutoff condition (e.g., a cutoff time, a cutoff ordervolume) is met if the lower-quality batch and/or the higher-qualitybatch is unsaturated (e.g., wherein the order volume too low to enabledrop-shipping, to meet a print partner's minimum order volumerequirement, etc.). In a third specific example, determining a batch fora digital asset with a flexible permutation can include preferentiallyassigning the digital asset to an existing batch that meets thepermutation requirements (e.g., to the existing potential batch that isalmost saturated, to the existing potential batch that is furthest fromsaturation, etc.), and optionally later moving the digital asset to anew batch that meets the permutation requirements (e.g., to ensure thatthe new batch meets a saturation condition). In a fourth specificexample, determining a batch for a digital asset with a flexiblepermutation can include optimizing for each batch of a set of candidatebatches to reach saturation (e.g., minimize the remaining digital assetsto saturation).

In a sixth variant, a delivery score can be determined for each digitalasset for each of a set of carrier facilities, wherein the digital assetis assigned to a batch, associated with a carrier facility, based on thescore. The delivery score can be indicative of: the estimated printtime, the estimated delivery time, the estimated cost (e.g., overallcost, print partner cost, delivery cost, etc.), the estimated carbonunits needed to deliver the physical asset, probability of the digitalasset contributing to saturation condition satisfaction for the carrierfacility, and/or indicative of any other suitable metric. The deliveryscore can be: calculated, predicted (e.g., using a neural network,etc.), and/or otherwise determined. The delivery score can be determinedbased on: the asset permutations, the characteristics of existingbatches (e.g., the volume in each batch, the asset permutations for eachbatch, the probability of each batch reaching saturation, etc.), thecharacteristics of the carrier facilities (e.g., saturation volume,etc.), and/or any other suitable input. The digital asset can beassigned to the batch associated with the highest-scoring carrierfacility, lowest-scoring carrier facility, and/or any other suitablecarrier facility.

In a seventh variant, S150 can include determining a batching date(e.g., two days prior to the target delivery date for the digital asset,a predicted print and ship duration prior to the target delivery date,etc.) and/or batching time for each of the digital assets that arereceived, and assigning each digital asset to the respective batch onthe respective batching date and/or at the respective batching time.

However, the batch can be otherwise determined.

5.3. Routing the Digital Asset to a Print Partner Based on the MailParameters S200.

Routing the digital asset to a print partner based on the mailparameters S200 preferably functions to determine a print partner withthe highest probability of printing and inserting a physical version ofthe digital asset into the mail stream with sufficient time to arrive atthe delivery location by a predetermined delivery date. The digitalasset can be routed individually or routed in batches, where all digitalassets in the same batch share a common set of mail parameters (e.g.,common local facility, common regional facility, common super-regionalfacility, common permutation, common target delivery date, etc.), and/orotherwise routed. S200 can be performed after S150, using any of themethods described in S150, instead of S150, and/or otherwise performed.

The digital asset (or set thereof) is preferably routed to a capableprint partner, but can be routed to any other print partner. Capableprint partners can have: the capability to print the digital asset/set(e.g., the print partner can print the permutation associated with thedigital asset/set) and the capacity to print the digital asset/set(e.g., the print partner has the capacity to print the volume of assetsin the digital asset set for the production day associated with thedigital asset set, etc.), or be otherwise defined. The capable printpartner(s) can also be determined based on the delivery location of eachdigital asset, and/or be geographically associated with the digitalasset set at one or more levels. For example, the capable printpartner(s) can be associated with the same: local facilities (e.g.,local geographic regions), regional facilities (e.g., regionalgeographic regions), super-regional facilities (e.g., super-regionalgeographic regions), national facilities (e.g., national geographicregions), and/or any other facilities or geographic regions as thedigital asset/set. When multiple capable print partners are availablefor a given digital asset set, a final print partner can be selectedfrom the capable print partner set.

The final print partner can be selected: manually (e.g., after a humanoperator calls the print partner by phone to verify that they can acceptthe order), randomly, based on a weight (e.g., select the highest- orlowest-weighted print partner, wherein the weight can be determined asdiscussed in U.S. application Ser. No. 17/127,125 filed 18 Dec. 2020,which is incorporated in its entirety by this reference, and/orotherwise determined), based on historical batch assignment (e.g.,wherein print partners that have been recently assigned batches are lesspreferred than others), based on physical proximity to the targetcarrier facility (e.g., that the digital asset set should bedrop-shipped to), based on production speed, based on an optimization,and/or otherwise selected. For example, a print partner can be selectedby optimizing facility assignment across multiple batches (e.g., tominimize the time-to-delivery for multiple batches, to minimize errorfrom the target delivery date for multiple batches, etc.); by optimizingover cost and/or time (e.g., drop-ship cost, time to print, time fromdigital asset receipt to delivery at the carrier facility, etc.); and/oroptimizing over any other suitable set of parameters.

However, the print partner can be otherwise selected for a digital assetset.

The capable print partner for a digital asset or a batch thereof can bedetermined: before batching, after batching, and/or any other suitabletime. The digital asset can be automatically routed to the printpartner, or alternatively only routed upon receipt of a confirmation(e.g., that the print partner still has remaining capacity).

In a first variant, S200 can include geo-routing. Geo-routing ispreferably applied to individual digital assets, but can alternativelybe applied to batches of digital assets (e.g., wherein digital assetsfrom one or more orders can be batched together based on similar mailparameters), and/or otherwise applied. Geo-routing can include routing adigital asset to a capable print partner within a region based on thedelivery destination (e.g., within the destination's zip code, within aspecified distance of a mail carrier facility servicing the destination,etc.). In a first embodiment, geo-routing can include routing eachdigital asset to a capable print partner that is closest to the deliverylocation.

In a second embodiment, geo-routing includes: routing the digital assetto the lowest-level facility servicing the digital asset's deliverylocation. For example, geo-routing can include: routing the digitalasset to a local capable print partner associated with a local facility(e.g., a DDU) servicing the digital asset's delivery location; when nolocal print partner is available, routing the digital asset to aregional capable print partner associated with a regional facility(e.g., an SCF) servicing the digital asset's delivery location; when noregional print partner is available, routing the digital asset to asuper-regional capable print partner associated with a super-regionalfacility (e.g., an NDC) servicing the digital asset's delivery location;and when no super-regional capable print partner is available, routingthe digital asset to a national capable print partner associated with anational facility servicing the digital asset's delivery location orrouting to a print partner using a method as discussed in U.S.application Ser. No. 17/127,125 filed 18 Dec. 2020, which isincorporated in its entirety by this reference. The print partner can beassociated with a facility when the print partner is the geographicallyclosest capable print partner to the facility, when the print partner islocated within a predetermined distance of the facility, when the printpartner is within the facility's geographic region, and/or be otherwiseassociated with the facility.

In a second variant, S200 can include zip-based routing; example shownin FIG. 3 . Zip-based routing can include: assigning the digital assetto a regional batch S210, sending the regional batch to a print partnerwhen a first threshold condition (e.g., a saturation condition) issatisfied S220, assigning digital assets of the regional batch to asecondary batch at a cut-off time when the first threshold condition isnot satisfied S230, sending the secondary batch to a print partner whena second threshold condition is satisfied S240, and optionallyindividually sending each digital asset of the secondary batch to printpartners when the second threshold condition is not satisfied S250.However, zip-based routing can be otherwise performed.

In S210, the digital asset is preferably assigned to a batch sharing allor a portion of the digital asset's permutation, but can be otherwiseassigned. The digital assets within the batch preferably have deliverylocations serviced by the same facility, but can alternatively havedelivery locations serviced by different facilities (e.g., of the sameor different hierarchical level). The facility is preferably a regionalfacility (e.g., such that the batch is a regional batch), but canalternatively be a local facility or a facility at another hierarchicallevel. The digital assets within the batch can have the same ordifferent: target delivery dates, production days (e.g., receipt date,routing date, print date, print partner assignment date, etc.), and/orany other parameter. The resultant batch can be identified by a batchidentifier (e.g., a combination of contextual and asset parameters suchas permutation:production_day), or be otherwise identified.

In a first example, each digital asset is assigned to a regionalfacility, and one or more batches are created for each regionalfacility. Each digital asset can be assigned to a regional facilitybased on: the delivery location (e.g., wherein the delivery location iswithin the regional facility's geographic region), the estimateddelivery speed (e.g., whether the asset will be delivered to thedelivery location at the target delivery date and/or date range if theasset is drop-shipped to the regional facility), and/or otherwisedetermined. Batches can then be created based on shared permutations. Acapable print partner can be assigned to the batch before or after batchcreation (e.g., wherein a capable print partner has capacity for digitalasset volume associated with a saturation condition).

In a second example, digital assets are batched by a shared permutationand/or a shared location identifier (e.g., by a 3-digit zip, by a5-digit zip, etc.) to determine a batch. A capable print partner canthen be assigned to the batch before or after batch creation (e.g.,wherein a capable print partner has capacity for digital asset volumeassociated with a saturation condition).

In a third example, S210 includes assigning a digital asset to aregional facility based on a delivery location, determining a capableprint partner associated with the regional facility, adding the digitalasset to an existing batch for the capable print partner if it exists,and creating a new batch if no existing batch for the capable printpartner exists. An existing batch preferably has the same permutation asthe digital asset, but can alternatively have a different permutation.The existing batch can be created using this method, created using amethod as discussed in U.S. application Ser. No. 17/127,125 filed 18Dec. 2020, which is incorporated in its entirety by this reference,and/or otherwise created. Creating a new batch with a print partner caninclude reserving a minimum volume from the capable print partner'scapacity, and optionally creating a digital object representative of thebatch (e.g., array, variable instance, etc.).

In an illustrative example, S210 includes, for a production day:determining a permutation and a delivery location associated with adigital asset; determining a 3-digit zip code based on the deliverylocation; determining a regional facility associated with the 3-digitzip code; assigning the digital asset to an existing batch having thesame permutation for the regional facility; optionally decrementing theavailable capacity for the print partner assigned to the existing batch;when no existing batch exists, creating a new batch with a print partnerclosest to the regional facility that has the capability for thepermutation and the capacity for a new batch (e.g., the minimumdrop-ship volume); optionally decrementing the available capacity forthe print partner by the capacity for the new batch (e.g., to reservecapacity in advance since it takes time to aggregate thousands oforders); and assigning the digital asset to the new batch; example shownin FIG. 4 .

Sending the regional batch to a print partner when a saturationcondition is satisfied S220 functions to start printing the digitalassets when the batch can be drop-shipped. The saturation condition(e.g., print condition, threshold condition, etc.) can be: a cutofftime, a minimum digital asset volume, and/or any other suitablethreshold condition. The regional batch is preferably sent to a printpartner when a saturation condition is satisfied before a routingcut-off time, but can alternatively be sent to a print partner when asaturation condition is satisfied after a routing cut-off time. Theprint partner is preferably the print partner associated with theregional batch (e.g., located within the regional carrier facilitydelivery zone, located within a threshold distance of the regionalcarrier facility, etc.), but can alternatively be a different printpartner. The print partner can be assigned to the regional batch at orduring batch formation, after batch formation, and/or at any othersuitable time. The print partner can have the capacity to print thebatch, the capabilities to print the permutations within the batch,and/or be otherwise characterized.

The regional batch can be sent: immediately when a saturation conditionis satisfied (e.g., on the production day, the day the batch is created,the day is digital asset is routed, etc.), on a print partnertransmission day (e.g., a future production day), and/or any othersuitable time. The print partner transmission day can be calculatedbased on the target delivery date and/or date range (e.g., assuming theprint partner will not hold onto the physical assets post printing), orbe otherwise determined. For example, the print partner transmission daycan be determined by: estimating a delay before printing; estimating thetime it takes to print the batch (e.g., for the print partner, onaverage, etc.); estimating the amount of time it takes for a printpartner to drop-ship, estimating the time it takes to deliver thephysical asset from the drop-shipped facility to the delivery location;and back-calculating a print partner transmission day by subtracting thetime estimates from the target delivery date and/or date range. Theestimates can be derived from historical print partner data and/orcarrier data (e.g., a print partner transmission time, a carrierinsertion time, a carrier delivery time, etc.), but can be otherwisedetermined.

S220 can optionally include sending other digital assets associated withthe permutation to the print partner. Other digital assets can beassociated or unassociated with the regional facility (e.g., have adelivery location outside of the regional facility's geographic region).For example, other digital assets can be associated with the printpartner using: zip-based routing (e.g., assigned to the routed regionalbatch), geo-routing, the method discussed in U.S. application Ser. No.17/127,125 filed 18 Dec. 2020, which is incorporated in its entirety bythis reference, and/or any other suitable method.

Assigning digital assets of the regional batch to a secondary batch at acut-off time when the saturation condition is not satisfied S230functions to roll up multiple regional batches into a larger batch,which has a higher probability of satisfying the saturation conditionprior to a cut-off time. The secondary batch is preferably associatedwith another carrier facility, more preferably a carrier facility at ahigher hierarchical level, but alternatively a carrier facility at thesame hierarchical level (e.g., a associated with a physically adjacentcoverage region with the carrier facility) and/or a lower hierarchicallevel (e.g., associated with an overlapping coverage region with thefirst carrier facility). The secondary batch can be iteratively reformedfor one or more carrier facilities (e.g., a predetermined series ofcarrier facilities). For example, the secondary batch can be a nationalbatch (e.g., associated with a national carrier facility), a secondaryregional batch (e.g., associated with a physically adjacent regionalcarrier facility), and/or any other suitable carrier facility. Thecut-off time is preferably earlier than the production day associatedwith the regional batch, but can alternatively be any other suitabletime. In a first example, the cut-off time is the routing cut-off time.In a second example, the cut-off time is the production day.

S230 can include batching together all regional batches that: share thesame permutation, are associated with the same super-regional facility,that have not met the saturation condition, have met the saturationcondition but satisfy a rollup condition (e.g., have batch sizes smallerthan a second threshold volume), and/or any other suitable set ofregional batches. The batched regional batches can be batched into anational batch, into another regional batch (e.g., a regional batch fora region adjacent or within a threshold geographic distance from theregion of the original regional batch), and/or into any other suitablebatch. However, the super batch (e.g., national batch) can be otherwisecreated. In examples, the national batch can be identified by a nationalbatch identifier (e.g., permutation:print_partner:national_facility:production_day) or otherwise identified.

S230 can additionally include assigning a capable print partner to thesecondary batch (e.g., “secondary print partner”, “national printpartner”). The capable print partner can be assigned before or afternational batch creation. The secondary print partner can be: a regionalprint partner associated with one of the constituent regional batches; acapable print partner assigned de novo (e.g., based on physicalproximity to the national facility, based on location within thenational facility's geographic region, etc.); and/or otherwisedetermined.

S230 can additionally include resetting and/or updating the capacity ofthe print partner associated with the regional batch if a hold wasplaced on the regional print partner capacity. For example, the capacityof the print partner associated with the regional batch can be increasedby the decremented amount in S210.

In an illustrative example, S230 includes: resetting the capacity of theprint partner associated with the regional batch; determining a nationalfacility affiliated with the regional facility defined by the regionalbatch; determining if a secondary batch associated with the permutation,print partner, national facility, and production day exists; creating asecondary batch if it doesn't already exist; once a secondary batch iscreated, decrementing the capacity of the print partner associated withthe secondary batch by a predetermined unit (e.g., the nationalfacility's drop-ship minimum, a minimum volume, a maximum volume, etc.);and assigning the digital assets of the regional batch to the secondarybatch.

Sending the secondary batch to a print partner when a saturationcondition is satisfied S240, enables the national print partner to printa batch of physical assets that can be drop-shipped. S240 can beperformed at: a cut-off time, when the secondary batch is formed, aftera cut-off time, before a production cut-off time, before a productionday, and/or any other suitable time. The saturation condition ispreferably the same saturation condition as S220, but can alternativelybe a different saturation condition. The saturation condition ispreferably associated with a minimum volume (e.g., determined by a mailpartner, determined by a print partner), but can alternatively beassociated with a minimum weight (e.g., digital asset weight), a maximumweight, a maximum volume, and/or any other suitable threshold. The printpartner is preferably a print partner associated with the secondarybatch, but can alternatively be a print partner closest to the nationalfacility with capability and capacity, and/or any other suitable printpartner.

Individually sending each digital asset of the secondary batch when thesaturation condition is not satisfied S250 functions to un-batch thenational and/or regional batches into constituent digital assets, andindividually route each digital asset. S250 can optionally includeresetting and/or updating the capacity of the print partner associatedwith the secondary batch if a hold was placed on the secondary printpartner capacity and/or any other suitable element. S250 is preferablyperformed using the method described in the first variant of S200 (e.g.,geo-routing), but can alternatively be performed using the method asdiscussed in U.S. application Ser. No. 17/127,125 filed 18 Dec. 2020,which is incorporated in its entirety by this reference, and/or anyother suitable method. For example, S250 includes: for each digitalasset within the secondary batch, determining a set of print partnersthat have the capability and capacity to print the digital asset, anddetermining a print partner from the subset based on the deliverylocation of the digital asset. In a first specific example, the printpartner is determined from the subset by selecting the print partnerfrom the subset within the delivery location's local geographic area;example shown in FIG. 6 . In a second specific example, the printpartner is determined from the subset by selecting the print partnerfrom the subset within the delivery location's regional geographic areaif a print partner from the subset within the delivery location's localgeographic area does not exist; example shown in FIG. 7 . In a thirdspecific example, the print partner is determined from the subset byselecting the print partner from the subset within the deliverylocation's super-regional geographic area if a print partner from thesubset within neither the delivery location's local geographic area northe delivery location's regional geographic area do not exist; exampleshown in FIG. 8 .

In another illustrative example, S200 can be executed by implementing adecision tree-based algorithm (e.g., example shown in FIG. 10 ). Asorders are received, digital assets from the orders are assigned toregional batches (individually or in sets) based on the asset'spermutation and delivery location. Optionally, a new regional batch canbe created (e.g., automatically, manually, etc.) each time a digitalasset with a unique combination of permutation and delivery location isreceived. Optionally, a regional batch can be assigned to a regionalprint partner once a regional batch reaches saturation (e.g., when thenumber of digital assets assigned to the regional batch exceed athreshold), or before the regional batch reaches saturation (e.g.,wherein a minimum batch volume can be reserved from the print partner'scapacity). Additionally or alternatively, at a cutoff time (e.g., on themorning of the production date, the afternoon before the productiondate, etc.) a decision-making process is implemented to determine aprint partner for each regional batch. For each regional batch, aregional print partner is associated with the regional batch if theregional batch has reached saturation; otherwise, the regional batch isrolled up to a national batch with an overlapping carrier zone (e.g.,wherein the national carrier facility's delivery zone encompasses theregional carrier facility's delivery zone). Subsequently, each nationalbatch is checked for saturation, and assigned a national print partnerif saturated. If a national batch is not saturated, the algorithmdetermines whether there is at least one corresponding regional batch(e.g., defined by a regional carrier facility that has a coverage regionencompassed by or overlapping with the coverage region of the nationalcarrier facility) that is fully saturated. If so, one of thecorresponding regional batches is selected to be rolled up into thenational batch (e.g., wherein the regional batch with the smallest batchsize is selected). Once all regional batches have been assigned to aprint partner or rolled up to a national branch, each regional batchwill be fully saturated, but not all national batches will necessarilybe fully saturated. All saturated batches can be assigned to a printpartner. The digital assets of any unsaturated batches can optionally begeo-routed to their respective delivery locations, and/or assigned to aprint partner in another manner.

In a third variant, S200 can include speed-based routing. In thisvariant, the asset is routed to the fastest facility (e.g., routed to aprint partner associated with the fastest facility, example shown inFIG. 9 ), and/or the fastest print partner.

The facility is preferably a super-regional facility, but canadditionally and/or alternatively be a regional facility, a localfacility, and/or any other suitable facility. The facility that theasset is routed to can be: the fastest facility (e.g., super-regionalfacility), the least congested facility (e.g., super-regional facility),and/or otherwise determined. The fastest facility and/or the fastestprint partner can be determined using a congestion and/or speedprediction model, using a set of heuristics, an optimization, a rule,and/or otherwise determined. The model preferably leverages regression(e.g., a random forest regression), but can additionally and/oralternatively be an equation, a neural network (e.g., trained to predictfacility congestion), leverage classification, rules, heuristics,decision trees, probability, and/or any other suitable model ormethodology. The model is preferably trained on historical congestiondata (e.g., tracking data) for the specific facility, but canalternatively be trained on historical congestion data (e.g., trackingdata) for similar facilities (e.g., facilities located in the samegeographic region, facilities of the same class, etc.; from the same ordifferent carrier) and/or any other data. The model (and underlyingtraining data) can be specific to: a recurrent timeframe (e.g., weeks,months, seasons, weather, fiscal quarters, etc.); a geographic region; atimeframe measured from the current time (e.g., a 2-week period fromlast month); any other spatial and/or temporal combination; generic(e.g., spatially and/or temporally); and/or otherwise specific ornonspecific. In an illustrative example, the model can identify patternsof congestion within super-regional facilities, such that physicalassets can be routed to the fastest or least congested super-regionalfacility (e.g., for more reliable and predictable service).

Routing the asset to the fastest facility can include: routing the assetto a print partner associated with the fastest facility (e.g., the printpartner that is already associated with a batch for the fastestfacility; a print partner within a predetermined physical distance ortravel time of the fastest facility; etc.); creating a batch for a printpartner associated with the fastest facility; routing the asset to anyother suitable print partner; and/or otherwise routing the asset to thefastest facility. The model outputs can be used to route assets in thismethod, in the method discussed in U.S. application Ser. No. 17/540,521filed on 2 Dec. 2021 which is incorporated herein in its entirety bythis reference, and/or otherwise used.

In a fourth variant, S200 can include cost-based routing. In thisvariant, the asset is routed to the facility that will reduce the costsassociated with printing and/or shipping, while meeting a shippingtimeframe. The lowest-cost facility can be determined with respect tothe asset, a batch containing the asset, or a set of batches.

Cost-based routing can incorporate elements of any of the other variantsto determine a set of potential facilities that are predicted to ensurethe digital asset will arrive within a shipping timeframe associatedwith the digital asset. The lowest-cost facility can be determined fromthe set of potential facilities.

The lowest-cost facility and/or the lowest-cost print partner can bedetermined using a cost prediction model, using a set of heuristics,using a set of historical data, using a set of published prices, and/orotherwise determined. The model preferably leverages regression (e.g., arandom forest regression), but can additionally and/or alternatively bean equation, a neural network (e.g., trained to predict costs associatedwith printing and shipping), leverage classification, rules, heuristics,decision trees, probability, optimization, and/or any other suitablemodel or methodology. The model is preferably trained on historical costdata (e.g., cost tracking data) for the specific facility, but canalternatively be trained on historical cost data for similar facilities(e.g., facilities located in the same geographic region, facilities ofthe same class, etc.; from the same or different carrier), publisheddata (e.g., determined from a website), and/or any other data. The model(and underlying training data) can be specific to: a recurrent timeframe(e.g., weeks, months, seasons, weather, fiscal quarters, etc.); ageographic region; a timeframe measured from the current time (e.g., a2-week period from last month); any other spatial and/or temporalcombination; generic (e.g., spatially and/or temporally); and/orotherwise specific or nonspecific. The data that is leveraged can relateto the costs associated with an individual print partner (e.g., pricescharged), the costs of shipping (e.g., fuel, truck driver pay per hour,etc.), the costs associated with a facility (e.g., UPS vs FedEx shippingcosts), and/or any other costs incurred in the printing and shippingprocess. In an illustrative example, the model can identify patterns ofcost fluctuation across facilities and print partners (e.g., acrossseasons), such that physical assets can be routed to a print partnersuch that the total costs associated with printing with the printpartner and shipping with the closest facility to the printer areminimized.

However, the digital asset can be otherwise routed.

5.4. Printing a Physical Version of Each Digital Asset S300.

Printing a physical version (e.g., a physical analog) of each digitalasset S300 functions to create the physical asset for each digitalasset. S300 is preferably performed by the print partner that thedigital asset was routed to (e.g., individually or as part of a batch),but can alternatively be performed by a mail partner, and/or any othersuitable entity. Printing the physical asset (e.g., the physical versionof the digital asset) can include: setting up the print machine based onthe digital asset's permutation, optionally aggregating a digital proofof the digital asset (e.g., from a programmatic representation of thedigital asset, from a tabular representation of the digital asset,etc.), and printing the physical asset based on the digital asset usingthe machine. One or more physical assets for a digital asset can beprinted. Physical assets for one or more digital assets can be printed:concurrently, contemporaneously, serially, and/or with any othersuitable temporal relationship. The physical asset is preferably printedat a print time, but can alternatively be printed at a random time,and/or any other suitable time.

In a first variant, the print time is specified by the platform (e.g.,back calculated based on an estimate time to print for the printpartner, time for the print partner to drop-ship to a facility, and timeto deliver to delivery location from the drop-ship facility, etc.).

In a second variant, the print time is determined by the print partner.

In a third variant, the print time is the production day.

However, the print time can be any other suitable time.

However, the physical version of each digital asset can be otherwiseprinted.

5.5. Drop-Shipping the Physical Assets S400.

Drop-shipping the physical assets S400 functions to send the physicalassets to a facility to be drop-shipped. The physical assets arepreferably drop-shipped as a batch, but can alternatively bedrop-shipped individually, and/or in any other suitable manner. Thebatch can be the same batch routed in S200, but can alternatively be adifferent batch. The batch can include: only digital assets within therouted batch, but can alternatively include other digital assets. Thephysical assets are preferably drop-shipped by a print partner (e.g.,associated with the batch), but can alternatively be drop-shipped by acarrier, a third-party transportation system, and/or any other suitableentity. The physical assets are preferably drop-shipped to the carrierfacility associated with the batch, but can alternatively bedrop-shipped to another carrier facility (e.g., an adjacent carrierfacility, a higher-level carrier facility encompassing the originalcarrier facility, etc.), and/or drop-shipped to another facility. Thecarrier facility to drop-ship to (and/or other drop-ship parameters,such as drop-ship time, location, etc.) can be provided to the printpartner for association with the batch of physical assets (e.g., withthe digital asset information; using an API; etc.), provided to thecourier transporting the batch of physical assets to the carrierfacility, and/or otherwise provided. The physical assets are preferablydrop-shipped at a drop-ship time, but can alternatively be drop-shippedat a random time, and/or any other suitable time.

In a first variant, the drop-ship time is specified by the platform(e.g., calculated based on an estimated time to delivery).

In a second variant, the drop-ship time is determined by a printpartner.

However, the drop-ship time can be any other suitable time.

However, the physical assets can be otherwise drop-shipped.

All references cited herein are incorporated by reference in theirentirety, except to the extent that the incorporated material isinconsistent with the express disclosure herein, in which case thelanguage in this disclosure controls.

Different processes and/or elements discussed above can be performed andcontrolled by the same or different entities. In the latter variants,different subsystems can communicate via: APIs (e.g., using API requestsand responses, API keys, etc.), requests, and/or other communicationchannels. Communications between systems can be encrypted (e.g., usingsymmetric or asymmetric keys), signed, and/or otherwise authenticated orauthorized.

Alternative embodiments implement the above methods and/or processingmodules in non-transitory computer-readable media, storingcomputer-readable instructions that, when executed by a processingsystem, cause the processing system to perform the method(s) discussedherein. The instructions can be executed by computer-executablecomponents integrated with the computer-readable medium and/orprocessing system. The computer-readable medium may include any suitablecomputer readable media such as RAMs, ROMs, flash memory, EEPROMs,optical devices (CD or DVD), hard drives, floppy drives, non-transitorycomputer readable media, or any suitable device. The computer-executablecomponent can include a computing system and/or processing system (e.g.,including one or more collocated or distributed, remote or localprocessors) connected to the non-transitory computer-readable medium,such as CPUs, GPUs, TPUS, microprocessors, or ASICs, but theinstructions can alternatively or additionally be executed by anysuitable dedicated hardware device.

Embodiments of the system and/or method can include every combinationand permutation of the various system components and the various methodprocesses, wherein one or more instances of the method and/or processesdescribed herein can be performed asynchronously (e.g., sequentially),contemporaneously (e.g., concurrently, in parallel, etc.), or in anyother suitable order by and/or using one or more instances of thesystems, elements, and/or entities described herein. Components and/orprocesses of the following system and/or method can be used with, inaddition to, in lieu of, or otherwise integrated with all or a portionof the systems and/or methods disclosed in the applications mentionedabove, each of which are incorporated in their entirety by thisreference.

As a person skilled in the art will recognize from the previous detaileddescription and from the figures and claims, modifications and changescan be made to the preferred embodiments of the invention withoutdeparting from the scope of this invention defined in the followingclaims.

1. A system, configured to: receive an order comprising a set of digitalassets, each associated with a different delivery address; determine aset of batches, each associated with a carrier facility, wherein eachcarrier facility services a delivery region, wherein the carrierfacilities are arranged in a hierarchy; batch each of the digital assetsinto one of a set of batches based on the respective delivery addressfalling within the delivery region associated with the respective batch;select a print partner for each batch, wherein the print partner islocated proximal the respective delivery region; send the digital assetswithin a batch to the print partner when a threshold condition is met,wherein the print partner prints physical analogs of the digital assets;and when the threshold condition is not met, iteratively re-batchdigital assets from a batch into other batches associated with carrierfacilities at higher hierarchical levels, until a second thresholdcondition is met.
 2. The system of claim 1, wherein the print partnerdrop-ships the physical analogs to the carrier facility associated withthe batch.
 3. The system of claim 1, wherein each batch is specific toan asset permutation.
 4. (canceled)
 5. The system of claim 4, whereinthe second threshold condition is different from the thresholdcondition.
 6. The system of claim 1, wherein re-batching the digitalassets when the threshold condition is not met is further based on ashared zip code.
 7. A method comprising: receiving an order comprising aset of digital assets, wherein each digital asset is associated with adifferent delivery address; determining a batch for each digital assetbased on the respective delivery address, wherein the delivery addressis located within a common delivery region associated with the batch;and when a threshold condition is satisfied for a batch, determining aprint partner located proximal the common delivery region associatedwith the batch and sending the digital assets within the batch to theprint partner for physical asset printing, wherein the thresholdcondition comprises a quantity of digital assets assigned to the batchexceeding a threshold value.
 8. The method of claim 7, wherein thecommon delivery region is a delivery region of a carrier facility withina hierarchy of carrier facilities, wherein parent carrier facilities areassociated with delivery regions encompassing delivery regions of childcarrier facilities within the hierarchy, wherein the physical assets aredrop-shipped to the carrier facility.
 9. The method of claim 8, furthercomprising, when the threshold condition is not satisfied for a batch,iteratively re-batching the digital assets within the batch based ondelivery regions of carrier facilities at iteratively higherhierarchical levels until a second threshold condition is satisfied, anddetermining a print partner for the re-batched digital assets.
 10. Themethod of claim 9, wherein the second threshold condition is differentfrom the threshold condition.
 11. The method of claim 9, wherein thethreshold condition comprises a minimum dropship volume for the carrierfacility, and the second threshold condition comprises a minimum printvolume for the print partner.
 12. The method of claim 8, furthercomprising, when the threshold condition is not satisfied for a batch,iteratively re-batching the digital assets within the batch using apost-order search through the carrier facility hierarchy.
 13. The methodof claim 7, wherein the batch is printed by the print partner andsubsequently drop shipped.
 14. A method comprising: receiving an ordercomprising a set of digital assets, wherein each digital asset isassociated with a different delivery address; determining a batch foreach digital asset based on the respective delivery address, wherein thedelivery address is located within a common delivery region associatedwith the batch; when a threshold condition is satisfied for a batch,determining a print partner located proximal the common delivery regionassociated with the batch and sending the digital assets within thebatch to the print partner for physical asset printing; and when thethreshold condition is not satisfied for a batch, combining the batchwith another batch associated with an adjacent delivery region.
 15. Themethod of claim 7, wherein the common delivery region is a zip code. 16.The method of claim 7, wherein the batch comprises digital assets from aplurality of orders.
 17. The method of claim 7, further comprising: foreach batch, when the threshold condition is not satisfied for the batch,individually routing each digital asset of the batch to a capable printpartner within a mail carrier facility coverage zone that services therespective delivery address.
 18. (canceled)
 19. The method of claim 7,wherein the threshold value comprises a minimum print volume for theprint partner.
 20. The method of claim 7, further comprising, for afirst batch, after determining the print partner for the first batch:sending the first batch to the determined print partner; prior to acutoff time, receiving additional mail orders; determining additionaldigital assets from the additional mail orders to assign to the firstbatch; and sending the additional digital assets to the determined printpartner.